Information sharing program, information sharing system and information sharing method

ABSTRACT

A non-transitory computer-readable storage medium storing therein an information sharing program for causing a computer to execute a process includes storing, in a storage, conversion information including first processing request information for issuing a processing request to a first processing processor that operates on a first physical machine, first operating environment information relating to an operating environment of the first physical machine and corresponding to the first processing request information, and second operating environment information relating to an operating environment of a second physical machine and corresponding to second processing request information for issuing a processing request to a second processing processor that operates on the second physical machine, and when a virtual machine that operates on the first physical machine transfers to the second physical machine, causing the second physical machine to hold the conversion information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is based upon and claims the benefit of priority of theprior Japanese Patent Application No. 2014-203560, filed on Oct. 2,2014, the entire contents of which are incorporated herein by reference.

FIELD

The present invention relates to an information sharing program, aninformation sharing system and an information sharing method.

BACKGROUND

In recent years, with improvements in the performance of physicaldevices (also called “physical machines” below), research has beenadvancing in virtualization technology wherein a plurality of virtualdevices (also called “virtual machines” below) are integrated into onephysical machine. This virtualization technology makes it possible, forexample, to assign a physical machine to a plurality of virtual machinesby virtualization software (hypervisor) and to provide services byapplication programs (also called simply “applications” below) which areinstalled in the respective virtual machines.

In a virtual machine that is operating, all or a portion of the contents(called “disk image” below) making up the virtual machine may betransferred to a virtual machine created in another physical machine. Bythis means, an operator providing services (simply called “operator”below) can, for example, transfer the disk image of a virtual machinecreated in a physical machine which is close to a 100% CPU use rate, toa virtual machine created in another physical machine which has sparecapacity (see, for example, Japanese Laid-open Patent Publication No.2000-132403 and Japanese Laid-open Patent Publication No. 2004-158012).

SUMMARY

Physical machines on which virtual machines are operating may be runninga monitoring system for supervising the operational status of thevirtual machines or a billing system for billing a user of the servicesprovided by the virtual machines (also called simply “user” below), forexample. In these cases, the user sends a processing request to themonitoring system, or the like, via an application running on a virtualmachine, for example. The monitoring system, or the like, which receivesthe processing request executes processing corresponding to theprocessing request, and sends the result of the processing to thevirtual machine. Consequently, the user is able to acquire informationrelating to the current operational status of the virtual machine, orthe like.

Here, when virtual machines are transferred, there may occur cases wherethe representation of the information necessary to execute therespective processes differs between the monitoring system, or the like,running on the physical machine which is the transfer source, and themonitoring system, or the like, running on the physical machine which isthe transfer destination. In this case, the transferred virtual machinecannot associate the information used in order to carry out theprocessing request before transfer, with the information required inorder to carry out the processing request after transfer. Consequently,the transferred virtual machine may not be able to carry out theprocessing request in respect of a process running on thetransfer-destination physical machine.

According to an aspect of the embodiments, a non-transitorycomputer-readable storage medium storing therein an information sharingprogram for causing a computer to execute a process includes: storing,in a storage, conversion information including first processing requestinformation for issuing a processing request to a first processingprocessor that operates on a first physical machine, first operatingenvironment information relating to an operating environment of thefirst physical machine and corresponding to the first processing requestinformation, and second operating environment information relating to anoperating environment of a second physical machine and corresponding tosecond processing request information for issuing a processing requestto a second processing processor that operates on the second physicalmachine; and when a virtual machine that operates on the first physicalmachine transfers to the second physical machine, until transfer of thevirtual machine to the second physical machine is completed, causing thesecond physical machine to hold the conversion information.

The object and advantages of the invention will be realized and attainedby means of the elements and combinations particularly pointed out inthe claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory and arenot restrictive of the invention.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating an overall configuration of aninformation processing system.

FIG. 2 is a diagram illustrating the transfer of a virtual machine.

FIG. 3 is a diagram illustrating the transfer of a virtual machine.

FIG. 4 is a diagram illustrating the hardware configuration of aphysical machine.

FIG. 5 is a functional block diagram of the physical machine in FIG. 4.

FIG. 6 is a functional block diagram of the physical machine in FIG. 4.

FIG. 7 is a flowchart diagram illustrating an overview of an informationsharing process according to the first embodiment.

FIG. 8 is a flowchart diagram illustrating an overview of an informationsharing process according to the first embodiment.

FIG. 9 is a flowchart diagram illustrating an overview of an informationsharing process according to the first embodiment.

FIG. 10 is a diagram illustrating an overview of an information sharingprocess according to the first embodiment.

FIG. 11 is a diagram illustrating an overview of an information sharingprocess according to the first embodiment.

FIG. 12 is a flowchart diagrams illustrating the details of aninformation sharing process according to the first embodiment.

FIG. 13 is a flowchart diagrams illustrating the details of aninformation sharing process according to the first embodiment.

FIG. 14 is a flowchart diagrams illustrating the details of aninformation sharing process according to the first embodiment.

FIG. 15 is a flowchart diagrams illustrating the details of aninformation sharing process according to the first embodiment.

FIG. 16 is a flowchart diagrams illustrating the details of aninformation sharing process according to the first embodiment.

FIG. 17 is a diagram illustrating the details of an information sharingprocess according to the first embodiment.

FIG. 18 is a diagram illustrating the details of an information sharingprocess according to the first embodiment.

FIG. 19 is a diagram illustrating the details of an information sharingprocess according to the first embodiment.

FIG. 20 is a diagram illustrating the details of an information sharingprocess according to the first embodiment.

FIG. 21 is a diagram illustrating the details of an information sharingprocess according to the first embodiment.

FIG. 22 is a diagram illustrating the details of an information sharingprocess according to the first embodiment.

DESCRIPTION OF EMBODIMENTS

(Configuration of Information Processing System)

FIG. 1 is a diagram illustrating an overall configuration of aninformation processing system. The information processing system 10illustrated in FIG. 1 includes a management server 1 and physicalmachines 2 which creates virtual machines (VM), in a data center, forexample. The data center can be accessed from a user terminal 5 via anetwork, such as an Intranet or the Internet.

The physical machines 2 are configured by a plurality of physicalmachines in the example in FIG. 1, and each physical machine has acentral processing unit (CPU), a random access memory (RAM), and alarge-capacity memory, such as a hard disk (hard disk drive (HDD)), andthe like. The resources of the physical machines 2 are allocated to aplurality of virtual machines 3.

A management server 1 is capable of accessing the physical machines 2,for example, and issues instructions for creating virtual machines 3 inthe physical machines 2, as well as managing the virtual machines 3 thatare created.

The virtual machines 3, for example, are used by an operator to provideinfrastructure services to users via a network (for example, cloudservices). A cloud service is a service in which the actual basis forconstructing and operating a computer system, in other words,infrastructure in itself such as virtual machines 3 and/or networks,etc., is provided via a network. Furthermore, a user accesses a cloudservice portal site from a user terminal 5, for example, and selects thespecifications required in the virtual machines, for example, the CPUclock frequency, memory capacity (GB), hard disk capacity (MB/sec,IOPS), and the network communication bandwidth (Gbps), and enters into acloud use contract in respect of same. Furthermore, the user terminal 5is also able to monitor the operational state of the virtual machines 3and/or regulate the virtual machines, and so on.

The virtualization software 4 is basic software which operates thevirtual machines 3 by allocating the CPU, memory, hard disk and networkof the physical machines 2, in accordance with instructions from themanagement server 1. The virtualization software 4 runs on a physicalmachine 2, for example.

The virtual machines 3, in addition to receiving allocation of resourcesof the physical machines 2, have, in the hard disks thereof, an imagefile including an operating system (OS), middle ware, applications,database, and the like. The virtual machine 3 writes the image file tothe memory from the hard disk upon starting up, and performs operationsin accordance with the desired services.

(Transfer of a Virtual Machine)

Next, the transfer of a virtual machine will be described. FIGS. 2 and 3are diagrams illustrating the transfer of a virtual machine.

In the example illustrated in FIG. 2, a virtual machine 31A, a virtualmachine 32A and a monitoring system 21A (also called “first processingunit 21A” below) are provided in the physical machine 2A. Furthermore,the physical machine 2A has hardware 22A. On the other hand, a virtualmachine 31B and a monitoring system 21B (also called “second processingunit 21B” below) are provided in the physical machine 2B. Moreover, thephysical machine 2B has hardware 22B.

The monitoring systems 21A, 21B in the example in FIG. 2, for example,each periodically access the hardware 22A, 22B, and acquire the useamount of the resources (for example, CPU and/or memory) of the hardware22A, 22B used by the virtual machines. If the use amount of theresources used by the virtual machines exceeds the upper limit of apredetermined range, then the monitoring systems 21A and 21B request themanagement server 1 illustrated in FIG. 1 to create a new virtualmachine. Furthermore, the monitoring systems 21A, 21B request thedeletion of any of the virtual machines which have been created by themanagement server 1 illustrated in FIG. 1, if the use amount of theresources used by the virtual machines is lower than a lower limit ofthe predetermined range. Consequently, the operator can efficientlycreate and delete virtual machines, and can restrict the used amount ofthe resources of the physical machines.

More specifically, in the example illustrated in FIG. 2, when it isdetected that the use amount of the resources of the hardware 22A isgreater than the upper limit of the predetermined range, then themonitoring system 21A sends the management server 1 a request for thetransfer of the virtual machine 31A or the virtual machine 32A toanother physical machine. As illustrated in FIG. 3, for example, themanagement server 1 then transfers the virtual machine 32A to thephysical machine 2B. Accordingly, the operator can restrict the useamount of the resources of the hardware 22A of the physical machine 2.

Here, for example, the monitoring system 21A and the monitoring system21B may have different representations, etc. of the information requiredin order for the virtual machines to carry out processing requests. Morespecifically, this corresponds to a case where, for example, in themonitoring system 21A, the information corresponding to the user nameand password is represented as “User” and “Password”, whereas in themonitoring system 21B, the information is represented as “Login” and“PWD”. Therefore, even if, for instance, the transferred virtual machine32A has information such as the user name used in the monitoring system21B, the virtual machine 32A is not able to associate this with the username, etc. used in the monitoring system 21A. Therefore, the virtualmachine 32A after transfer is not able to carry out the processingrequest in the monitoring system 21B, in this case.

On the other hand, there are cases where, for instance, the informationrequired in order to carry out a processing request in the monitoringsystem 21B is set previously in the virtual machine 32A that is beingtransferred. However, the information required in order to carry out theprocessing request in the monitoring system 21B may be information thatis first defined when the transferred virtual machine 32A is started upin the physical machine 2B. Therefore, the operator cannot previouslyset all of the information required in order to carry out a processingrequest in the monitoring system 21B, in the virtual machine 32A beforetransfer. Consequently, the operator must interrupt the provision ofservices by the virtual machine 32A after transfer of the virtualmachine 32A, and set the information for carrying out a processingrequest in the monitoring system 21B.

Therefore, in the present embodiment, in accordance with the transfer ofa virtual machine 32A, the transfer-destination physical machine 2B ismade to hold information for carrying out a processing request to theprocesses running in the transfer-source physical machine 2A, andinformation relating to the environments of the transfer-source physicalmachine 2A and the transfer-destination physical machine 2B.Consequently, the operator is able to prevent the interruption ofservices in association with the transfer of a virtual machine 32A.

(Hardware Configuration of Physical Machines)

Next, the configuration of the physical machines 2A, 2B will beexplained. FIG. 4 is a diagram illustrating the hardware configurationof a physical machine. The physical machine 2A (also called “firstphysical machine 2A” below) has a CPU 201A, which is a processor, amemory 202A, an external interface (I/O unit) 203A, and a storage medium204A. These respective parts are connected to each other via a bus 205A.The storage medium 204A stores a program 210A for carrying outprocessing for sharing information between the physical machine 2A andthe physical machine 2B (called “information sharing process” below), ina program storage region (not illustrated) in the storage medium 204A,for example. The CPU 201A, as illustrated in FIG. 4, loads the program210A to the memory 202A from the storage medium 204A, each time theprogram 210A is executed, and carries out an information sharing processin collaboration with the program 210A. Furthermore, the storage medium204A has, for example, an information storage region 230A (also called“storage unit 230A” below) which stores information used when carryingout the information sharing process.

Moreover, the physical machine 2B (also called the “second physicalmachine 2B” below) has, similarly to the physical machine 2A, a CPU 201Bwhich is a processor, a memory 202B, an external interface (I/O unit)203B and a storage medium 204B. These parts are connected to each othervia a bus 205B. The storage medium 204B stores a program 210B forcarrying out the information sharing process, in a program storageregion (not illustrated) in the storage medium 204B. As illustrated inFIG. 4, the CPU 201B loads the program 210B from the storage medium 204Bto the memory 202B, each time the program 210B is executed, and carriesout the information sharing process in collaboration with the program210B. Moreover, the storage medium 204B has an information storageregion 230B (also called “storage unit 230B” below) which storesinformation used when carrying out the information sharing process.

(Functions of Physical Machine)

FIG. 5 and FIG. 6 are functional block diagrams of the physical machinein FIG. 4. The CPU 201A of the physical machine 2A, by operating incollaboration with the program 210A, operates as a transfer detectionunit 211A, an information storage unit 212A, a request acquisition unit213A, a request conversion unit 214A, and a request transmission unit215A, for example. Furthermore, the CPU 201A, by operating incollaboration with the program 210A, operates as an information requestunit 216A, an authentication request unit 217A, and an authenticationacquisition unit 218A, for example. Moreover, processing requestinformation 231A (also called “first processing request information231A” below), operating environment information 232A (also called “firstoperating environment information 232A” below), conversion information233A and argument conversion information 234A are stored in theinformation storage region 230A. Below, the transfer detection unit211A, the information management unit 212A, the request acquisition unit213A, the request conversion unit 214A, the request transmission unit215A, the information request unit 216A, the authentication request unit217A and the authentication acquisition unit 218A are jointly called a“conversion unit 220A”.

Furthermore, the CPU 201B of the physical machine 2B, by operating incollaboration with the program 210B, operates as a transfer detectionunit 211B, an information management unit 212B, a request acquisitionunit 213B, a request conversion unit 214B, and a request transmissionunit 215B, for example. Furthermore, the CPU 201B, by operating incollaboration with the program 210B, operates as an information requestunit 216B, an authentication request unit 217B, and an authenticationacquisition unit 218B, for example. Moreover, processing requestinformation 231B (also called “second processing request information231B” below), operating environment information 232B (also called“second operating environment information 232B” below), conversioninformation 233B and argument conversion information 234B are stored inthe information storage region 230B. Below, the transfer detection unit211B, the information management unit 212B, the request acquisition unit213B, the request conversion unit 214B, the request transmission unit215B, the information request unit 216B, the authentication request unit217B and the authentication acquisition unit 218B are jointly called a“conversion unit 220B”.

(Functions of Transfer Detection Unit and Information Management Unit)

The transfer detection unit 211A of the physical machine 2A detects whena virtual machine has been transferred to the physical machine 2A fromanother virtual machine, for example.

The information management unit 212A of the physical machine 2A stores,in the information storage region 230A, the processing requestinformation 231A for carrying out a processing request in respect of thefirst processing unit 21A operating on the physical machine 2A, from thevirtual machine (the application running on the virtual machine) whichis operating on the physical machine 2A, for example. More specifically,when the processing request information 231A has been input from theuser, for example, the information management unit 212A stores the inputprocessing request information 231A in the information storage region230A. The processing request information 231A may include authenticationinformation (for example, a user name and password) in order for thefirst processing unit 21A to carry out authentication in respect of thevirtual machine (or the user of the virtual machine). Furthermore, theprocessing request information 231A may include argument information forrequesting processing of the first processing unit 21A, for example. Thedetails of the processing request information 231A are describedhereinafter. Furthermore, the argument conversion information 234A forcarrying out conversion of the argument information is describedhereinafter.

Furthermore, the information management unit 212A stores, for example,conversion information 233A including the processing request information231A, the operating environment information 232A relating to theoperating environment of the physical machine 2A, and the operatingenvironment information 232B relating to the operating environment ofthe physical machine 2B. The operating environment information 232A isinformation corresponding to the processing request information 231A,for example, and may be identification information 232A which enablesthe physical machine 2A to identify the type of the processing requestinformation 231A. Furthermore, the operating environment information232B is information corresponding to the processing request information231B, for example, and may be identification information 232B whichenables the physical machine 2B to identify the type of the processingrequest information 231B. Moreover, when creating the conversioninformation 233A, the information management unit 212A associates theoperating environment information 232A and the operating environmentinformation 232B which have information of the same contents.Consequently, the physical machine 2A or the physical machine 2B is ableto convert the processing request information 231A into processingrequest information 231B corresponding to the operating environmentinformation 232B which has the same contents as the operatingenvironment information 232A corresponding to the processing requestinformation 231A. Specific examples of the operating environmentinformation 232A, 232B and the conversion information 233A, 233B aredescribed below.

Moreover, the information management unit 212A, for example, when thetransfer detection unit 211A has detected the transfer of a virtualmachine relating to the physical machine 2A, acquires the conversioninformation stored in the transfer-source physical machine up to thecompletion of the transfer of the virtual machine. The informationmanagement unit 212A then stores the conversion information for thetransfer-source physical machine, in the information storage region230A, as conversion information 233A. Consequently, the physical machine2A is able to acquire, cumulatively, the conversion information inrespect of all of the physical machines on which the virtual machinebeing transferred has operated in the past.

The transfer detection unit 211B and the information management unit212B of the physical machine 2B carry out the same processing as thetransfer detection unit 211A and the information management unit 212Bdescribed above, and therefore description thereof is omitted here.Furthermore, the processing request information 231B and the argumentconversion information 234B are the same as the processing requestinformation 231A and the argument conversion information 234A, andtherefore description thereof is omitted here.

(Functions of Request Acquisition Unit, Request Conversion Unit, RequestTransmission Unit and Information Request Unit)

The request acquisition unit 213A of the physical machine 2A acquiresprocessing request information sent to the first processing unit 21A bythe virtual machine operating on the physical machine 2A, for example.In other words, when a virtual machine operating on the physical machine2A is a virtual machine that has been transferred from another physicalmachine, then the processing request information acquired by the requestacquisition unit 213A is processing request information which it is notclear that the first processing unit 21A can recognize.

The request conversion unit 214A of the physical machine 2A, forexample, determines whether or not the conversion information 233Aincludes processing request information 231A which corresponds to theprocessing request information transmitted from the virtual machineoperating on the physical machine 2A. In other words, the requestconversion unit 214A determines whether or not processing requestinformation 231A which has the same contents as the processing requestinformation acquired by the request acquisition unit 213A and which canbe processed by the first processing unit 21A is included in (is presentin) the conversion information 233A. If the conversion information 233Aincludes processing request information 231A corresponding to theprocessing request information acquired by the request acquisition unit213A, then the request conversion unit 214A instructs the requesttransmission unit 215A to transmit the processing request information231A that was included in the conversion information 233A, to the firstprocessing unit 21A. On the other hand, if the conversion information233A does not include processing request information 231A correspondingto the processing request information acquired by the requestacquisition unit 213A, then the information request unit 216A of thephysical machine 2A requests the input of processing request information231A, by the user of the virtual machine operating on the physicalmachine 2A. Consequently, the request conversion unit 214A is able tosend processing request information 231A which has the same contents asthe processing request information acquired by the request acquisitionunit 213A and which can be processed by the first processing unit 21A,to the first processing unit 21A. Moreover, if the processing requestinformation 231A is included in the conversion information 233A, thenthe physical machine 2A can send the processing request information 231to the first processing unit 21A, without requesting the processingrequest information 231A from the user of the virtual machine.Therefore, it is possible to prevent the interruption of the servicesprovided to the user by the physical machine 2A, even in the case of thetransfer of a virtual machine.

The request transmission unit 215A of the physical machine 2A sends theprocessing request information 231A to the first processing unit 21A, onthe basis of an instruction from the request conversion unit 214A, forexample.

The request acquisition unit 213B, the request conversion unit 214B, therequest transmission unit 215B and the information request unit 216B ofthe physical machine 2B carry out the same processing as the requestacquisition unit 213A, the request conversion unit 214A, the requesttransmission unit 215A and the information request unit 216A describedabove, and therefore description thereof is omitted here.

(Functions of Authentication Request Unit and Authentication AcquisitionUnit)

The authentication request unit 217A of the physical machine 2A, forexample, sends authentication information included in the processingrequest information 231A acquired by the request acquisition unit 213A,to the first processing unit 21A, and requests execution ofauthentication processing, by the first processing unit 21A.

The authentication acquisition unit 218A of the physical machine 2A, forexample, acquires authentication key information (also called simply“authentication key” below) sent by the first processing unit 21A. Theauthentication key is described hereinafter. Furthermore, specificexamples of the processing of the authentication request unit 217A andthe authentication acquisition unit 218A are also described hereinafter.The authentication request unit 217B and the authentication acquisitionunit 218B of the physical machine 2B carry out similar processing to theauthentication request unit 217A and the authentication acquisition unit218A and therefore description thereof is omitted here.

First Embodiment

Next, a first embodiment will be described. FIG. 7 to FIG. 9 areflowchart diagrams illustrating an overview of an information sharingprocess according to the first embodiment. Furthermore, FIG. 10 and FIG.11 are diagrams illustrating an overview of an information sharingprocess according to the first embodiment. An overview of theinformation sharing process in FIG. 7 to FIG. 9 is described here withreference to FIG. 10 and FIG. 11. A case where a virtual machineoperating on the physical machine 2A is transferred to the physicalmachine 2B will be described below. The points of difference betweenFIG. 10 and FIG. 11, and FIG. 2 and FIG. 3, will be described.

Firstly, the processing in the physical machine 2A (the conversion unit220A of the physical machine 2A) will be described. As illustrated inFIG. 7 and FIG. 10, the physical machine 2A waits until the timing atwhich conversion information 233A is stored, for example (NO at S1). Thetiming at which conversion information 233A is stored is, for example,when the virtual machine operating on the physical machine 2A has sentthe processing request information 231A to the first processing unit21A. When the timing for storing conversion information 233A is reached(YES at S1), the physical machine 2A creates conversion information 233Aincluding the processing request information 231A sent from the virtualmachine operating on the physical machine 2A, the operating environmentinformation 232A, and the operating environment information 232B. Thephysical machine 2A then stores the created conversion information 233Ain the storage unit 230A (S2). In other words, the physical machine 2A,for example, accumulates and stores the conversion information 233A inthe information storage region 230A, in accordance with the sending ofthe processing request information 231A to the first processing unit 21Afrom the virtual machine operating on the physical machine 2A. Theoperating environment information 232A and the operating environmentinformation 232B may be stored previously in the information storageregion 230A. Furthermore, the operator may previously store conversioninformation 233A including the processing request information 231A, inthe storage unit 230A, before sending the processing request information231A to the first processing unit 21A.

Next, the processing in the physical machine 2B (the conversion unit220B of the physical machine 2B) will be described. As illustrated inFIG. 8 and FIG. 11, the physical machine 2B waits, for example, for thetransfer of a virtual machine to the physical machine 2B to be carriedout (NO at S11). When a virtual machine operated on the physical machine2A is transferred to the physical machine 2B for example (YES at S11),then the physical machine 2B holds the conversion information 233Astored in the storage unit 230A of the physical machine 2A (S12). Morespecifically, the physical machine 2B may access the storage unit 230A,for example, to acquire the conversion information 233A, and to storesame in the storage unit 230B as conversion information 233B.Furthermore, the physical machine 2B may receive the conversioninformation 233A sent from the physical machine 2A and store same in theinformation storage region 230B as conversion information 233B.

Consequently, the physical machine 2B is able to refer to the conversioninformation 233B when the virtual machine that has been transferred fromthe physical machine 2A to the physical machine 2B, sends the processingrequest information 231A to the second processing unit 21B. The physicalmachine 2B, by referring to the conversion information 233B, is able toacquire processing request information 231B corresponding to theoperating environment information 232B having the same contents as theoperating environment information 232A corresponding to the processingrequest information 231A of the transferred virtual machine. Therefore,the physical machine 2B can determine whether or not the processingrequest information 231B corresponding to the processing requestinformation 231A of the virtual machine is present in the conversioninformation 233B.

The physical machine 2B may acquire a conversion module for operatingthe conversion unit 220A (for example, a portion of the program 210Aillustrated in FIG. 4), jointly when acquiring the conversioninformation 233A from the physical machine 2A. The physical machine 2Bmay operate as a conversion unit 220B by running the acquired conversionmodule in collaboration with the CPU. Furthermore, the physical machine2A may store the conversion module and the conversion information 233Ain a different physical machine to the physical machine 2A. Furthermore,if the conversion information 233A includes information relating tothree or more physical machines, then the physical machine 2B mayacquire only the information relating to the physical machine 2A and thephysical machine 2B, from among the conversion information 233A.Similarly, if the conversion information 233A includes informationrelating to three or more physical machines, then the physical machine2B may acquire only a conversion module for converting the processingrequest information 231A and the processing request information 231B.

Thereafter, as illustrated in FIG. 9 and FIG. 11, the physical machine2B waits for the processing request information 231A to be sent to thesecond processing unit 21B from the virtual machine that has beentransferred from the physical machine 2A (NO at S21). When theprocessing request information 231A has been sent from the transferredvirtual machine (YES at S21), then the physical machine 2B, for example,refers to the conversion information 233B, and determines whether or notprocessing request information 231B corresponding to the sent processingrequest information 231A is present (S22). More specifically, the secondprocessing unit 21B cannot recognise the processing request information231A sent by the virtual machine 32A and therefore cannot carry outprocessing based on the processing request information 231A.Consequently, the physical machine 2B acquires (traps) the processingrequest information 231A sent by the virtual machine 32A, and if theprocessing request information 231B is present in the conversioninformation 233B, converts the processing request information 231A intoprocessing request information 231B that can be processed by the secondprocessing unit 21B.

Thereupon, if processing request information 231B corresponding to theprocessing request information 231A is present (YES at S22), then thephysical machine 2B, for example, sends the processing requestinformation 231B to the second processing unit 21B (S23). In otherwords, in this case, the physical machine 2B, by referring to theconversion information 233B, is able to automatically convert theprocessing request information 231A sent by the transferred virtualmachine 32A into the processing request information 231B. Therefore, thephysical machine 2B, in this case, does not need to request the input ofinformation required in order to carry out the processing request in thesecond processing unit 21B.

On the other hand, if the processing request information 231Bcorresponding to the processing request information 231A is not present(NO at S22), then the physical machine 2B, for example, requests inputof the processing request information 231B, by the user of the virtualmachine. As illustrated in FIG. 11, for instance, when the correspondingprocessing request information 231B is input by the user via the userterminal 5, then the physical machine 2B sends the input processingrequest information 231B to the second processing unit 21B (S24).

In this way, according to the first embodiment, firstly, the physicalmachine 2A stores conversion information 233A including the processingrequest information 231A for carrying out the processing request in thefirst processing unit 21A which is operating on the physical machine 2A,and the operating environment information 232A and the operatingenvironment information 232B, in the storage unit 230A. The physicalmachine 2B then holds the conversion information 233A (conversioninformation 233B) in accordance with the transfer of the virtual machinefrom the first physical machine 2A to the second physical machine 2B.Thereby, the physical machine 2B is able to determine whether or notprocessing request information 231B corresponding to the processingrequest information 231A sent by the virtual machine 32A is present inthe conversion information 233B.

According to the first embodiment, the physical machine 2B refers to theconversion information 233B when a virtual machine that has beentransferred sends processing request information 231A and issues aprocessing request to the second processing unit 21B. Subsequently, thephysical machine 2B determines whether or not processing requestinformation 231B corresponding to the operating environment information232B which has the same contents as the operating environmentinformation 232A corresponding to the processing request information231A of the transferred virtual machine is present in the conversioninformation 233B. If, as a result of this, the corresponding processingrequest information 231B is present, then the physical machine 2B sendsthe processing request information 231B in the conversion information233B, to the second processing unit 21B. On the other hand, if thecorresponding processing request information 231B is not present, thenthe physical machine 2B, after input of the processing requestinformation 231B that was not present, sends the processing requestinformation 231B that has been input, to the second processing unit 21B.Thereby, if the processing request information 231B corresponding to theprocessing request information 231A sent by the transferred virtualmachine is present in the conversion information 233B, then the operatordoes not need to set the processing request information 231B inassociation with the transfer of the virtual machine. Consequently, inthis case, the operator is able to prevent the interruption of servicesin association with the transfer of the virtual machine.

The physical machine 2B, upon receiving processing results (hereinafteralso called a response) relating to the processing request information231A sent by the virtual machine which has transferred to the physicalmachine 2B, may send the processing results to the virtual machine thatissued the processing request. In this case, for example, if thephysical machine 2B has converted the processing request information231A into the processing request information 231B and sent thisinformation to the second processing unit 21B, then the physical machine2B refers to the conversion information 233B. The physical machine 2Bmay send the received processing results after reconverting toinformation that can be recognized by the virtual machine which sent theprocessing request information 231A. Thereby, the transferred virtualmachine (the application of the transferred virtual machine) is able torecognise the response from the second processing unit 21B, even ifthere is a difference between the processing request information 231Asent by the virtual machine, and the processing request information 231Bthat has actually been processed by the second processing unit 21B.

(Details of First Embodiment)

Next, the details of the first embodiment will be described. FIG. 12 toFIG. 16 are flowchart diagrams illustrating the details of aninformation sharing process according to the first embodiment.Furthermore, FIG. 17 to FIG. 22 are diagrams illustrating the details ofan information sharing process according to the first embodiment. Thedetails of the information sharing process illustrated in FIG. 12 toFIG. 16 are described with reference to FIG. 17 to FIG. 22. Below, theprocessing request information 231A is described as includingauthentication information 241A for the first processing unit 21A tocarry out authentication of the virtual machine, and argumentinformation 242A which is an argument for requesting specific processingto the first processing unit 21A. Similarly, the processing requestinformation 231B is described as including authentication information241B and argument information 242B.

(Processing in First Physical Machine)

Firstly, as illustrated in FIG. 12, the request acquisition unit 213A ofthe physical machine 2A waits for processing request information 231Arelating to the first processing unit 21A to be sent from the virtualmachine which is operating on the physical machine 2A, for example (NOat S31). When processing request information is sent from the virtualmachine operating on the physical machine 2A (YES at S31), then therequest acquisition unit 213A traps the processing request informationthat has been sent. More specifically, the request acquisition unit 213Areceives all of the processing request information sent from the virtualmachines operating on the physical machine 2A. Thereby, the requestconversion unit 214A becomes able to determine whether or not conversionis required (whether or not the acquired processing request informationis the processing request information 231A), in respect of all of theprocessing request information acquired by the processing acquisitionunit 213A.

Next, the request conversion unit 214A of the physical machine 2Adetermines whether or not the authentication information contained inthe processing request information acquired by the request acquisitionunit 213A is present in the conversion information 233A stored in theinformation storage region 230A (S32). The authentication informationis, for example, information for the first processing unit 21A, etc. tocarry out authentication of the virtual machine. More specifically, theauthentication information may include a user name and password. If thefirst processing unit 21A, etc. has carried out authentication of thevirtual machine, then as described hereinafter, the informationmanagement unit 212A stores the authentication information used for thisauthentication in the information storage region 230A as a portion ofthe conversion information 233A. Therefore, the request conversion unit214A is able to determine whether or not the virtual machine that sentthe processing request information is a virtual machine that has alreadybeen authenticated by the first processing unit 21A, by determiningwhether or not the authentication information acquired by the requestacquisition unit 213A is present in the conversion information 233A.

If the authentication information contained in the processing requestinformation acquired by the request acquisition unit 213A is present inthe conversion information 233A (YES at S32), then the requestconversion unit 214A, for example, may determine whether or not theacquired authentication information is authentication information 241Acorresponding to the first processing unit 21A (S33). If, as a result ofthis, the acquired authentication information is not authenticationinformation 241A corresponding to the first processing unit 21A (NO atS33), then the information management unit 212A, for example, may storethe acquired authentication information in the information storageregion 230A as a portion of the conversion information 233A (S34). Inother words, a case where the acquired authentication information is notthe authentication information 241A corresponding to the firstprocessing unit 21A is a case where the conversion information 233Acontains other authentication information (authentication informationfor a processing unit operating on another physical machine, etc.),which has the same contents as the authentication information 241A forwhich a processing request has been made of the first processing unit21A. In this case, the request conversion unit 214A may determine thatthe acquired authentication information is authentication information241A corresponding to the first processing unit 21A, on the basis of thefact that other authentication information is present in the conversioninformation 233A. Thereby, the request conversion unit 214A is able torestrict the frequency with which the user is requested to inputauthentication information 241A.

On the other hand, if the authentication information contained in theprocessing request information acquired by the request acquisition unit213A is not present in the conversion information 233A (NO at S32), thenthe information request unit 216A, for example, requests the input ofauthentication information 241A corresponding to the first processingunit 21A (S35). Thereafter, the information request unit 216A, forexample, waits for the input of the authentication information 241A ofwhich the input has been requested (NO at S36). If there is an input ofauthentication information 241A (YES at S36), then the informationmanagement unit 212A stores the input authentication information 241A inthe information storage region 230A as a portion of the conversioninformation 233A (S37). A concrete example of the conversion information233A is described below.

FIG. 17 is a concrete example of the conversion information 233A. Theconversion information 233A illustrated in FIG. 17 includes, as items, a“process name” which identifies the monitoring system, etc. running oneach physical machine, and “metadata” which identifies the respectiveinformation managed by the conversion information 233A. Furthermore, theconversion information 233A illustrated in FIG. 17 includes, as items,“operating environment information” which identifies informationcorresponding to metadata in each of the processing units, and“authentication information” which is authentication information set foreach element of operating environment information.

More specifically, in the conversion information 233A illustrated inFIG. 17, “MON-A”, “MON-B” and “MON-C” are set as the “process name”.Furthermore, in the conversion information 233A illustrated in FIG. 17,“user name”, “password” and “authentication key” are set as “metadata”.The authentication key is described hereinafter. Furthermore, in theconversion information 233A illustrated in FIG. 17, in the “operatingenvironment information” corresponding to the “user name”, “User” is setfor “MON-A”, “Login” is set for “MON-B”, and “User” is set for “MON-C”.

The information set in the “operating environment information”illustrated in FIG. 17 is set already in the conversion information233A, before the request acquisition unit 213A acquires the processingrequest information 231A. Therefore, each physical machine is able tomake a processing request to each of the processing units, correspondingto the differences in the names, etc. of the information elementsrequired in each processing unit. More specifically, for example, the“password” in the “metadata” of FIG. 17 is represented as “Password” in“MON-A” and “MON-C”, but is represented as “PWD” in “MON-B”. The otherinformation in FIG. 17 is not described here.

FIG. 18 is an example of conversion information 233A illustrating a casewhere authentication information 241A (user name and password)corresponding to the first processing unit 21A is stored in S34 or S37,after the state illustrated in FIG. 17. Below, an example is describedwhere the information is stored in S34. Furthermore, in the followingdescription, it is supposed that the first processing unit 21A and theMON-A are mutually corresponding.

More specifically, information corresponding to a user name and passwordfor executing MON-A is not set in the conversion information 233Aillustrated in FIG. 17 (NO at S32). Therefore, as illustrated in FIG.18, the information management unit 212A sets the user name and passwordincluded in the input processing request information (S35, YES at S36,S37). More specifically, in the example illustrated in FIG. 18, theinformation management unit 212A sets “A531”, which is the input username, in the “authentication information” corresponding to theinformation of which the “process name” is “MON-A” and the “metadata” is“user name”. As illustrated in FIG. 18, the information management unit212A sets the input password “1234” in the “authentication information”corresponding to the information of which the “process name” is “MON-A”and the “metadata” is “password”. Consequently, after the state in FIG.18, when the processing request information 231A is sent again from thevirtual machine operating on the physical machine 2A, the requestconversion unit 214A does not need to set the processing requestinformation 231A that has been sent.

The virtual machine operating on the physical machine 2A may send theprocessing request information 231A which includes the operatingenvironment information illustrated in FIG. 18, etc. More specifically,the virtual machine which is running on the physical machine 2A sendsthe processing request information 231A in a state in which, forexample, “User”, which is in the operating environment information, isassociated with “A531”, which is in the authentication information, andin which “Password”, which is in the operating environment information,is associated with “1234”, which is in the authentication information.Therefore, the request conversion unit 214A, in S32, is able todetermine whether or not the authentication information contained in theprocessing request information acquired by the request acquisition unit213A is present in the conversion information 233A.

Returning to FIG. 13, the authentication request unit 217A of thephysical machine 2A, for example, determines whether or not theconversion information 233A includes an authentication key correspondingto the first processing unit 21A (S41). The authentication key is, forexample, information which is assigned to a virtual machine operating onthe physical machine 2A by the first processing unit 21A, on the basisof the user name and password sent to the first processing unit 21A bythe virtual machine.

If the authentication key corresponding to the first processing unit 21Ais not present in the conversion information 233A (NO at S41), then theauthentication request unit 217A of the physical machine 2A, forexample, sends the user name and password included in the conversioninformation 233A to the first processing unit 21A, and issues anauthentication request to the first processing unit 21A (S42). Theauthentication acquisition unit 218A of the physical machine 2A, forexample, waits for the first processing unit 21A to send anauthentication key (NO at S43). Thereafter, when the authenticationacquisition unit 218A has acquired an authentication key (YES at S43),the information management unit 212A, for example, stores the acquiredauthentication key in the storage unit 230A in association with theconversion information 233A (S44). If the authentication acquisitionunit 218A does not acquired an authentication key, then theauthentication acquisition unit 218A may return to S35. On the otherhand, if an authentication key corresponding to the first processingunit 21A is present in the conversion information 233A (YES at S33 orYES at S41), then the authentication request unit 217A does not carryout processing for acquiring the authentication key, etc. Accordingly,the authentication acquisition unit 218A is able to acquire anauthentication key, when authentication by the authentication requestunit 217A has been completed.

FIG. 19 is an example of conversion information 233A illustrating a casewhere an authentication key corresponding to MON-A has been stored (S44)after the state illustrated in FIG. 18. More specifically, asillustrated in FIG. 19, the information management unit 212A sets theauthentication key “2b3kkdzi7”, which is the authentication key acquiredby the authentication acquisition unit 218A, in the “authenticationinformation” corresponding to the information for which the “processname” is “MON-A” and the “metadata” is “authentication key”.

Returning to FIG. 13, after S44, or a YES result in S33, the requestconversion unit 214A, for example, acquires an authentication keycorresponding to the first processing unit 21A from the informationstorage region 230A (S45). Furthermore, the request conversion unit214A, for example, acquires argument information 242A corresponding tothe argument information contained in the processing request informationacquired by the request acquisition unit 213A by referring the argumentconversion information 234A (S46). More specifically, the requestconversion unit 214A converts not only the authentication informationcontained in the processing request information acquired by the requestacquisition unit 213A but also the argument information in order thatthe first processing unit 21A is able to execute the processing requestthat has been issued by the virtual machine.

FIG. 20 is a diagram illustrating a concrete example of the argumentconversion information 234A. The argument conversion information 234Aillustrated in FIG. 20 includes, as items, the “process name”illustrated in FIG. 18, the “metadata” illustrated in FIG. 18, and“argument information” to which the argument information 242A is set. Inthe “metadata” of the example in FIG. 20, “CPU use informationacquisition command” which acquires the use information of the CPU ofeach virtual machine, and “memory use information acquisition command”which acquires the use information of the memory of each virtualmachine, are set. More specifically, in the argument conversioninformation 234A illustrated in FIG. 20, “AAA” is set in the “argumentinformation” corresponding to the information for which the “processname” is “MON-A” and the “metadata” is “CPU use information acquisitioncommand”. The other information in FIG. 20 is not described here.

Returning to FIG. 13, the request transmission unit 215A sends theauthentication key acquired by the request conversion unit 214A in S45,and the argument information 242A acquired by the request conversionunit 214A in S46 (S47). In other words, the request transmission unit215A sends the authentication key jointly, when sending the argumentinformation 242A to the first processing unit 21A. Thereby, the requesttransmission unit 215A is not required to send the user name andpassword, each time the argument information 242A is sent. In this case,it is possible to reduce the processing load on the first processingunit 21A, since it is not necessary to carry out an authenticationprocess based on the user name and password, each time the argumentinformation 242A is received.

(Processing when Virtual Machine has Transferred from First PhysicalMachine to Second Physical Machine)

Next, the processing in a case where a virtual machine operating on thephysical machine 2A is transferred to the physical machine 2B will bedescribed. Firstly, the information management unit 212B of the physicalmachine 2B, as illustrated in FIG. 14, waits for the transfer of avirtual machine to the physical machine 2B, for example (NO at S51).When the virtual machine operating on the physical machine 2A istransferred to the physical machine 2B (YES at S51), then the physicalmachine 2B acquires and stores the conversion information 233A stored inthe storage unit 230A of the physical machine 2A (S52). In other words,the information management unit 212B, in S34 and S37 of FIG. 12, and S44of FIG. 13, acquires the conversion information 233A, which isinformation that has been stored by the information management unit212A. Therefore, the information management unit 212B can acquireconversion information corresponding to each of the physical machines onwhich the transferred virtual machine has operated in the past.

Thereupon, as illustrated in FIG. 15, the request acquisition unit 213Bof the physical machine 2B, similarly to the case of the physicalmachine 2A, for example, waits for the virtual machine operating on thephysical machine 2B to send processing request information correspondingto the second processing unit 21B (NO at S61). When processing requestinformation 231A is sent from the virtual machine that has transferredfrom the physical machine 2A to the physical machine 2B (YES at S61),then the request acquisition unit 213B, for example, traps thetransmitted processing request information 231A.

Next, the request conversion unit 214B of the physical machine 2B, forexample, determines whether or not the authentication information 241Acontained in the processing request information 231A acquired by therequest acquisition unit 213B is present in the conversion information233B stored in the information storage region 230B (S62). If theauthentication information 241A is present in the conversion information233B (YES at S62), then the request conversion unit 214B, similarly tothe case of the physical machine 2A, for example, determines whether ornot the acquired authentication information 241A is authenticationinformation 241B corresponding to the second processing unit 21B (S63).If, as a result of this, the acquired authentication information 241A isnot authentication information corresponding to the second processingunit 21B (NO at S63), then the information management unit 212B, forexample, stores the acquired authentication information 241B as aportion of the conversion information 233B (S64).

On the other hand, if the authentication information 241A contained inthe processing request information 231A acquired by the requestacquisition unit 213B is not present in the conversion information 233B(NO at S62), then the information request unit 216B, similarly to thecase of the physical machine 2A, for example, requests the input of thecorresponding authentication information 241B (S65). Thereafter, theinformation request unit 216B, for example, waits for the input of therequested authentication information 241B (NO at S66). When theauthentication information 241B is input (YES at S66), the informationmanagement unit 212B stores the input authentication information 241B inthe information storage region 230B as a portion of the conversioninformation 233B (S67). A concrete example of the conversion information233B is described below.

FIG. 21 is an example of the conversion information 233B illustrating acase where, after the state illustrated in FIG. 19, informationcorresponding to the user name and password corresponding to the secondprocessing unit 21B is stored in S64 or S67. Below, an example where theinformation is stored in S64 is described. Furthermore, in the followingdescription, it is supposed the second processing unit 21B and MON-B aremutually corresponding.

More specifically, the information corresponding to the user name andthe password for executing MON-B is not set in the conversioninformation 233B illustrated in FIG. 19 (NO at S62). Therefore, asillustrated in FIG. 21, the information management unit 212B sets theuser name and password contained in the processing request information231B acquired by the request acquisition unit 213B (S64). Morespecifically, in the example illustrated in FIG. 21, the informationmanagement unit 212B sets “142_A3”, which is the input user name, in the“authentication information” corresponding to the information for whichthe “process name” is “MON-B” and the “metadata” is “user name”. Asillustrated in FIG. 21, the information management unit 212B sets“24dfek”, which is the input password, in the “authenticationinformation” corresponding to the information for which the “processname” is “MON-B” and the “metadata” is “password”. More specifically,the information management unit 212B updates the conversion information233A acquired by the information management unit 212B. Consequently, theinformation management unit 212B is able to accumulate informationwithout recognizing the difference in the physical machines on which thetransferred virtual machine is operating.

Returning to FIG. 16, the authentication request unit 217B of thephysical machine 2B, similarly to the case of the physical machine 2A,for example, determines whether or not the authentication keycorresponding to the second processing unit 21B is included in theconversion information 233B (S71). If the authentication keycorresponding to the second processing unit 21B is not present in theconversion information 233B (NO at S71), then the authentication requestunit 217B of the physical machine 2B sends the user name and passwordincluded in the conversion information 233B, for example, to the secondprocessing unit 21B, and issues an authentication request to the secondprocessing unit 21B (S72). Thereupon, the authentication acquisitionunit 218B of the physical machine 2B waits for the first processing unit21A to send an authentication key (NO at S73). When the authenticationacquisition unit 218B acquires the authentication key (YES at S73), theinformation management unit 212B, for example, stores the acquiredauthentication key in the information storage region 230B in associationwith the conversion information 233B (S74). If the authenticationacquisition unit 218B does not acquired an authentication key, then theauthentication acquisition unit 218B may return to S65. On the otherhand, when the authentication key corresponding to the second processingunit 21B is present in the conversion information 233B (YES at S63 orYES at S71), then the authentication request unit 217B does not carryout processing for acquiring an authentication key, etc.

FIG. 22 is an example of conversion information 233B illustrating a casewhere, after the state illustrated in FIG. 21, the authentication keycorresponding to MON-B is stored (S74). In this case, the informationmanagement unit 212B, as illustrated in FIG. 22, sets “G49vk3xE”, whichis the authentication key acquired by the authentication acquisitionunit 218B, in the “authentication information” corresponding to theinformation for which the “process name” is “MON-B” and the “metadata”is “authentication key”.

Returning to FIG. 16, after S74 or a YES result in S63, the requestconversion unit 214B, for example, acquires the authentication keycorresponding to the second processing unit 21B from the informationstorage region 230B (S75). Furthermore, the request conversion unit 214Brefers to the argument conversion information 234B and converts theargument information 242A contained in the processing requestinformation 231A received in S71, to the argument information 242B whichcan be processed by the second processing unit 21B (S76).

More specifically, in the example in FIG. 20, when the argumentinformation contained in the processing request information 231A sentfrom the virtual machine that has transferred from the physical machine2A is “DDD”, then the request conversion unit 214B refers to theargument conversion information 234B. The request conversion unit 214Bthen acquires “FFF”, which is the information for which the “processname” is “MON-B” and which corresponds to “argument information” of“DDD”.

The request transmission unit 215B sends the authentication key acquiredby the request conversion unit 214B in S75, and the argument information242B converted by the request conversion unit 214B in S46 (S77).

In other words, the physical machines according to the presentembodiment progressively accumulate the processing request informationin the conversion information, each time a processing requestinformation is sent to the processing unit in the physical machine. Whena virtual machine operating on that physical machine is transferred toanother physical machine, for example, then conversion information inwhich the processing request information has been accumulated is sent tothe transfer-destination physical machine. Thereby, thetransfer-destination physical machine is able to accumulate newprocessing request information by updating the conversion informationreceived from the transfer-source physical machine, when new processingrequest information is sent from the virtual machine operating on thetransfer-destination physical machine. The physical machine thenconverts the processing request information by referring to theconversion information, and therefore it is possible to restrict thefrequency with which the input of processing request information isrequested of the user. Consequently, it is possible to restrict thefrequency with which interruption of services occurs in the physicalmachine.

All examples and conditional language provided herein are intended forthe pedagogical purposes of aiding the reader in understanding theinvention and the concepts contributed by the inventor to further theart, and are not to be construed as limitations to such specificallyrecited examples and conditions, nor does the organization of suchexamples in the specification relate to a showing of the superiority andinferiority of the invention. Although one or more embodiments of thepresent invention have been described in detail, it should be understoodthat the various changes, substitutions, and alterations could be madehereto without departing from the spirit and scope of the invention.

What is claimed is:
 1. A non-transitory computer-readable storage mediumstoring therein an information sharing program for causing a computer toexecute a process comprising: storing, in a storage, conversioninformation including first processing request information for issuing aprocessing request to a first processing processor that operates on afirst physical machine, first operating environment information relatingto an operating environment of the first physical machine andcorresponding to the first processing request information, and secondoperating environment information relating to an operating environmentof a second physical machine different from the first physical machineand corresponding to second processing request information for issuing aprocessing request to a second processing processor that operates on thesecond physical machine; and when a virtual machine that operates on thefirst physical machine transfers to the second physical machine, untiltransfer of the virtual machine to the second physical machine iscompleted, sending the conversion information from the first physicalmachine to the second physical machine; wherein when the virtual machineafter the transfer sends the first processing request information andissues a processing request to the second processing processor, thesecond physical machine refers to the conversion information; when thesecond processing request information corresponding to the secondoperating environment information and having the same contents as thefirst operating environment information corresponding to the firstprocessing request information is present in the conversion information,the second physical machine converts the first processing requestinformation corresponding to the processing request to the secondprocessing processor into the second processing request information thatis present in the conversion information and sends the second processingrequest information that is present in the conversion information to thesecond processing processor; and when the second processing processorsends a response relating to the second processing request informationsent to the second processing processor, the second physical machinerefers to the conversion information, reconverts the response intoinformation that can be recognized by the virtual machine after thetransfer and sends the information that can be recognized by the virtualmachine after the transfer to the virtual machine after the transfer. 2.The non-transitory computer-readable storage medium according to claim1, wherein when the second processing request information correspondingto the second operating environment information and having the samecontents as the first operating environment information corresponding tothe sent first processing request information is not present in theconversion information, the second physical machine sends the secondprocessing request information that has been input, to the secondprocessing processor, when the second processing request informationthat was not present has been input.
 3. The non-transitorycomputer-readable storage medium according to claim 2, wherein when thesecond processing request information that was not present has beeninput, the second physical machine stores the input second processingrequest information, in a storage, in association with the conversioninformation.
 4. The non-transitory computer-readable storage mediumaccording to claim 1, wherein the first and second processing requestinformation includes authentication information for the first processingprocessor or the second processing processor to carry out authenticationof the virtual machine.
 5. The non-transitory computer-readable storagemedium according to claim 1, wherein the first operating environmentinformation is information that enables the first physical machine toidentify a type of the first processing request information, and thesecond operating environment information is information that enables thesecond physical machine to identify a type of the second processingrequest information.
 6. An information sharing system comprising: afirst physical machine; and a second physical machine capable ofaccessing the first physical machine, wherein the first physical machinestores, in a storage, conversion information including first processingrequest information for issuing a processing request to a firstprocessing processor that operates on the first physical machine, firstoperating environment information relating to an operating environmentof the first physical machine and corresponding to the first processingrequest information, and second operating environment informationrelating to an operating environment of the second physical machinedifferent from the first physical machine and corresponding to secondprocessing request information for issuing a processing request to asecond processing processor that operates on the second physicalmachine; when a virtual machine that operates on the first physicalmachine transfers to the second physical machine, until transfer of thevirtual machine to the second physical machine is completed, sending theconversion information from the first physical machine to the secondphysical machine; when the virtual machine after the transfer sends thefirst processing request information and issues a processing request tothe second processing processor, the second physical machine refers tothe conversion information; when the second processing requestinformation corresponding to the second operating environmentinformation and having the same contents as the first operatingenvironment information corresponding to the first processing requestinformation is present in the conversion information, the secondphysical machine converts the first processing request informationcorresponding to the processing request to the second processingprocessor into the second processing request information that is presentin the conversion information and sends the second processing requestinformation that is present in the conversion information to the secondprocessing processor; and when the second processing processor sends aresponse relating to the second processing request information sent tothe second processing processor, the second physical machine refers tothe conversion information, reconverts the response into informationthat can be recognized by the virtual machine after the transfer andsends the information that can be recognized by the virtual machineafter the transfer to the virtual machine after the transfer.
 7. Aninformation sharing method, comprising: storing, by a first physicalmachine, in a storage, conversion information including first processingrequest information for issuing a processing request to a firstprocessing processor that operates on the first physical machine, firstoperating environment information relating to an operating environmentof the first physical machine and corresponding to the first processingrequest information, and second operating environment informationrelating to an operating environment of a second physical machinedifferent from the first physical machine and corresponding to secondprocessing request information for issuing a processing request to asecond processing processor that operates on a second physical machine;when a virtual machine that operates on the first physical machinetransfers to the second physical machine, until transfer of the virtualmachine to the second physical machine is completed, sending, by thefirst physical machine, the conversion information from the firstphysical machine to the second physical machine; when the virtualmachine after the transfer sends the first processing requestinformation and issues a processing request to the second processingprocessor, referring, by the second physical machine, to the conversioninformation; when the second processing request informationcorresponding to the second operating environment information and havingthe same contents as the first operating environment informationcorresponding to the first processing request information is present inthe conversion information, converting, by the second physical machine,the first processing request information corresponding to the processingrequest to the second processing processor into the second processingrequest information that is present in the conversion information andsends the second processing request information that is present in theconversion information to the second processing processor; and when thesecond processing processor sends a response relating to the secondprocessing request information sent to the second processing processor,referring, by the second physical machine, to the conversioninformation, reconverting, by the second physical machine, the responseinto information that can be recognized by the virtual machine after thetransfer and sending, by the second physical machine, the informationthat can be recognized by the virtual machine after the transfer to thevirtual machine after the transfer.